Open
Conversation
snan
commented
Mar 27, 2023
- Allow implementers to emit i and b
- Address the Gomphocarpus example
This example was not a correct use of strong or of em. (It's a good showcase for why strong and em are wrong.) Changed it to b and i, which the new rule 13 from the previous commit now allows. I'm putting this in a separate commit since another solution would be to change it to foo and bar.
Contributor
|
These examples are not just examples, they are test cases, which every single parser runs to verify spec conformance. So after this commit spec now mandates the use of different tags for the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.